Method and apparatus for mobile based access point name (apn) selection

ABSTRACT

A procedure is provided wherein a serving general packet radio service (GPRS) support node (SGSN) receives a request for an access point name (APN) the SGSN making a determination if the requested packet data protocol (PDP) and APN are the same as subscribed information. In the event that the requested and subscribed PDP type and the requested and subscribed APN are not the same, the SGSN advises that the APN requested is not authorized and agreement to terms and conditions and the provision of credit (or debit) card information must be provided to obtain the requested APN.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/228,619, filed Sep. 16, 2005, which is a continuation of Ser. No.10/321,331, filed Dec. 17, 2002, now U.S. Pat. No. 6,970,694, issuedNov. 29, 2005, which claims the benefit of U.S. Provisional ApplicationSer. No. 60/399,593, filed Jul. 30, 2002, which are incorporated byreference as if fully set forth.

FIELD OF INVENTION

The present invention relates to wireless communication systems. Moreparticularly, the invention relates to method and apparatus forpermitting access to an access point name (APN) not included within thesubscribers list of services.

BACKGROUND

Existing standardized APN selection procedures will result in a denialof service (reject packet data protocol (PDP) Context activationprocedures) in those cases where a mobile user has requested access to acertain APN not included within the list to which that user hassubscribed.

SUMMARY

The present invention provides a procedure in which a user is given anopportunity to access any APN he wishes provided that the user isadvised that he is not currently subscribed to this particular APN andthat additional charges will be billed to his account. The user may alsobe requested to provide credit/debit card (or the like) information tocover access and future traffic charges. If the user agrees to thecharges and/or provides credit/debit card information, i.e., paymentinformation, a serving general packet radio service (GPRS) support node,i.e. (SGSN) selects the requested APN and proceeds to select theappropriate GGSN for the requested APN.

The present invention extends existing standardized APN selectionprocedures enabling a user to select a domain name (APN) of his choice,even though not among his subscription list, providing that the userconsents/agrees to the applied charges for access and contents.

The technique of the present invention includes informing the user thathe is attempting to access a domain name that he is not authorized toaccess. The procedure requests that a user confirm his intent to accesssuch a domain by requesting financial verification which may be acredit/debit card, electronic check or the like, for billing access andtraffic charges. Upon agreement and verification, the SGSN selects therequested APN and the appropriate gateway GPRS support node (GGSN) tofacilitate the connection.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood from the accompanyingdescription and drawings wherein like elements are designated by likenumerals and, wherein:

FIG. 1 is a diagram useful in explaining the packet data protocol (PDP)context activation procedure.

FIG. 2 is a diagram useful in explaining overall GGSN selection.

FIG. 3 is a diagram showing the conventional APN selection procedure.

FIG. 4 is a diagram showing the APN selection procedures (SGSN) of thepresent invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

FIG. 1 shows a PDP context activation procedure in which the mobilestation 10, at step S1, activates a packet data protocol (PDP) contextrequest to SGSN14, which request includes information such as PDP type,PDP address, access point name (APN), quality of service (QoS) and thelike. The APN is used to select a reference point to a certain packetdata network and/or to select a service. SGSN 14, at step S2, validatesthe request, selects the requested APN and maps the APN to a GGSN, suchas GGSN 16. Thereafter, the SGSN, at step S3, creates the packet dataprotocol (PDP) context request which includes the PDP type, the PDPaddress, the access point name (APN), quality of service (QoS) and thelike. GGSN 16 creates the PDP context response including the tunnelendpoint identifier (TEID), PDP address, PDP configuration options, QoS,charging identification and cause, at step S4. At step S5, a radioaccess bearer (RAB) setup is created between SGSN 14 and radio accessnetwork (RAN) 12 (step S5A) and between the mobile station 10 and theradio access network (RAN) 12 (step S5B) utilizing a known RABassignment procedure. At step S6, SGSN 14 invokes a trace with RAN 12employing a known procedure.

At step S7, SGSN 14 updates the PDP context request to GGSN 16 and,responsive thereto, GGSN 16 updates the PDP context response, at stepS8. SGSN 14, at step S9, inserts the GGSN address into its PDP contextand sends the PDP address received from the GGSN 16 to mobile station 10and activates the PDP context accept at step S10 which includes PDPtype, PDP address, TI, QoS, radio priority, packet flow ID and PDPconfiguration options.

FIG. 2 is a diagram useful in explaining the overall GGSN selection. TheUE 10, also shown as the mobile station in FIG. 1, sends a requestincluding PDP type, PDP address and APN to SGSN 14. The SGSN 14 sendsthe APN and visited/home public land mobile network (V/H) PLMN-OI to thedirectory name service (DNS) database 16 which either provides the GGSNaddress shown at 18 or indicates an error at 20 if there is noassociated GGSN.

The SGSN 14 receives from the home location register (HLR) 22 thesubscribed: PDP type, PDP address, APN and the visited public landmobile network (VPLMN) address which is allowed. SGSN 14 also receivesthe SGSN access point name (APN) from defaults 24 provided in softwarewhich is hard-coded in SGSN 14.

FIG. 3 shows the existing procedure for APN selection wherein, at stepS1, the SGSN receives an activate PDP context request from the UE (note,for example UE 10 in FIG. 2). At step S2, the SGSN checks the optionalinformation which includes PDP type, PDP address and APN. If there is noinformation, at step S3, the SGSN, which branches to step S7, checks thesubscribed information and, at step S8, rejects the request if the UEhas multiple PDP subscriptions since only one PDP type can bedesignated. Alternatively, after performing the checking step S7, atstep S9, if the checking step indicates that the UE has a singlesubscription, the SGSN, branches to step S10 and provides subscribedinformation which includes the address mode, either dynamic or static,the PDP type and the subscribed APN of the SGSN if the subscribed APN isa wildcard and there is no APN request. WILDCARD=means that Any Name canbe used without causing any problems.

Returning to step S2, if there is only a PDP type request, determined atstep S4 and if the PDP type compares with the subscribed PDP type,determined at step S11 the routine jumps to step S10 wherein the SGSNprovides the same information as set forth above and as shown in stepS10.

Returning to step S11, if the PDP type is not the subscribed PDP typethe routine branches to step S12, causing the request to be rejected bythe SGSN.

Again returning to step S11, if the PDP type is the subscribed PDP typeand the PDP add request (PDP ADD (R)) is the same as the PDP addsubscribed, determined at step S13, the SGSN provides the data shown atstep S10. However, returning to step S13, if the PDP add request (PDPADD(R)) is not the same as the PDP add subscribed, the routine branchesto step S12 wherein the request is rejected. (R) here means Requested bythe UE. It may or may not be honored by the network depending on thesubscription information in the HLR.

Again returning to step S11, if the PDP type is the same as the PDP typesubscribed and, as determined at step S14, if the APN request is thesame as the APN subscribed, the SGSN branches to step S10 providing theinformation set forth therein. However, if the APN request is not thesame as the APN subscribed, the routine branches to step S12 in whichthe request is rejected.

Returning to step S2, if the PDP type request, the PDP type the PDPaddress and the APN are all present, the program, at step S16, branchesto step S11 to determine if the PDP type is the same as the PDP typesubscribed. If so, the program branches to step S14 wherein, if the APNrequested is the same as the APN subscribed, the SGSN provides theinformation shown in step S10. If the APN requested is not the same asthe APN subscribed, the routine branches to step S12 wherein the requestis rejected.

Returning to step S14, if the APN request is the same as the APNsubscribed the routine branches to step S15 wherein, if the PDP addrequest is the same as the PDP add subscribed, the SGSN provides theinformation set forth at step S10. Alternatively, if the PDP add request(PDP ADD (R)) is not the same as the PDP add subscribed, the routinebranches to step S12 in which the request is rejected.

FIG. 4 shows the extended APN selection procedure in accordance with thepresent invention wherein, when the SGSN, at step S1 receives theactivate PDP context request from the UE 10 (see FIGS. 1 and 2), theSGSN, at step S2, checks the optional information such as PDP type, PDPaddress and APN. If only the PDP type and APN are present, at step S3,the routine branches to step S4 to determine if the PDP type is thesubscribed PDP type. If not, the routine branches to step S5, rejectingthe request. If the PDP type is the same as the subscribed PDP type, theroutine branches to step S5 to examine the APN. If the requested APN isthe same as the subscribed APN, the routine branches to provide the sameinformation shown at step S10 in FIG. 3.

If the APN requested and the APN subscribed are not the same, theroutine branches to step S7 to inform the user that the APN requested isnot authorized and that if the UE (mobile station) wants to continue,the UE must agree to the terms and conditions and provide credit (ordebit) card or like information.

The SGSN, at step S8 examines the UE response and, if the terms andconditions are accepted, the routine branches to step S9 wherein therequested APN is selected. If the UE does not accept the terms andconditions, the routine branches to step S5 wherein the SGSN rejects therequest.

Returning to step S2, when the PDP type, PDP address and APN are allpresent, the routine branches to step S10 wherein steps S4 and S6 arerepeated and, dependent upon the results of these comparisons, theroutine branches to either steps S5, S7 or S10 of FIG. 3, the remainderof the routine being the same as described hereinabove for the casewhere only PDP type and APN are provided to the SGSN by the UE, shown instep S3 in FIG. 4.

1. A method comprising, a mobile station (UE): a) communicating to aserving general packet radio service (GPRS) support node (SGSN), apacket data protocol (PDP) context request to the network requesting aPDP type and an access point name (APN); the SGSN: b) validating therequest and mapping the APN to a gateway GPRS support node (GGSN); theGGSN: c) responding to the SGSN; the SGSN: d) advising the UE that it isnot authorized to receive the requested APN and that the UE must agreeto terms and conditions to access the requested APN when the PDP type isthe same as the PDP type subscribed and when the APN requested is notthe same as the APN subscribed for said UE; and the UE: e) acceptingsaid terms and conditions to obtain the requested APN.
 2. The method ofclaim 1 wherein step (d) includes sending a requirement that the UEconsent to charges, and further comprising. said UE communicatinginformation to the network to charge costs of obtaining said APN.
 3. Themethod of claim 2 wherein the step of communicating information tocharge costs of obtaining said APN further comprises communicatingcredit card information.
 4. The method of claim 1 further comprising,said UE receiving the requested APN.
 5. The method of claim 1 furthercomprising, said SGSN: rejecting the requested APN when a subscribed PDPtype of the UE is not the same as the requested PDP type.
 6. The methodof claim 1 further comprising, said UE communicating a rejection of theterms and conditions.
 7. The method of claim 1 further comprising, saidUE requesting a PDP address as part of said context request.
 8. Themethod of claim 1 further comprising, the SGSN providing a radio accessbearer (RAB) setup with the UE, employing a radio access network (RAN).9. The method of claim 1 wherein the SGSN, responsive the UE consentingto the terms, providing a radio access bearer (RAB) setup with the UE.10. The method of claim 9 wherein the SGSN provides the RAB setupemploying a radio access network (RAN).
 11. A method for a servinggeneral packet radio services (GRPS) support node (SGSN), whichprocesses a context request for an access point node (APN), said SGSNcomprising: a) checking subscribed information from a user equipment(UE) when none of a PDP type, a PDP address and an APN are present; b)rejecting the UE request if the UE has a multiple PDP subscription. 12.The method of claim 11 further comprising, said SGSN communicating therequested APN when the UE has a single subscription.
 13. The method ofclaim 12 further comprising, said SGSN communicating an address mode andPDP type as well as the requested APN when the UE has a singlesubscription.
 14. The method of claim 11 further comprising, said SGSNrejecting the context request when a subscribed PDP type is not the sameas the requested PDP type.
 15. The method of claim 11 furthercomprising, said SGSN providing an address mode and PDP type as well asthe requested APN when the requested PDP type is the same as asubscribed type.
 16. Apparatus configured as a serving general packetradio service (GRPS) support node (SGSN), comprising: a receiver forreceiving a context request requesting a packet data protocol (PDP)type, a PDP address, and an access point name (APN); a comparison devicefor determining if at least the PDP address requested compares withsubscribed data, and a device for granting the request when a comparisonis present.
 17. The apparatus of claim 16 wherein the granting device isconfigured to provide address mode and PDP type as well as the APN. 18.Apparatus configured as a serving general packet radio service (GRPS)support node (SGSN), comprising: a receiver for receiving a contextrequest requesting only a packet data protocol (PDP) type; a comparisondevice for determining if at least the PDP type requested compares withsubscribed data, and a device for granting the request when a comparisonis present.
 19. The apparatus of claim 18 wherein the granting device isconfigured to provide address mode and APN as well as PDP type. 20.Apparatus configured as a serving general packet radio service (GRPS)support node (SGSN), comprising: a receiver for receiving a contextrequest requesting only a packet data protocol (PDP) type and PDPaddress; a comparison device for determining if the PDP type and PDPaddress requested compares with subscribed data, and a device forgranting the request when a comparison is present.
 21. The apparatus ofclaim 20 wherein the granting device is configured to provide APN aswell as PDP type and PDP address.
 22. Apparatus configured as a servinggeneral packet radio service (GRPS) support node (SGSN), comprising: areceiver for receiving a context request requesting only an APN; acomparison device for determining if the APN requested compares withsubscribed data, and a device for granting the request when a comparisonis present.
 23. The apparatus of claim 22 wherein the granting device isconfigured to provide a PDP type and PDP address as well as therequested APN.
 24. The apparatus of claim 16 further comprising a devicefor rejecting the context request when at least one of the requested PDPtype and the PDP address is not the same as the subscribed criteria. 25.The apparatus of claim 18 further comprising a device for rejecting therequest when the PDP type requested does not compare with the storedcriteria.
 26. The apparatus of claim 20 further comprising a device forrejecting the request when at least one of the PDP type and PDP addressrequested does not compare with the stored criteria.
 27. Apparatus,comprising: a serving general packet radio service (GPRS) support node(SGSN); at least one gateway GPRS support node (GGSN); said SGSNconfigured for: receiving a context request requesting a packet dataprotocol (PDP) type and an access point name (APN) from a mobile unit(UE); examining the PDP type and APN request; validating the requestwhen the PDP type and APN requested compare with a subscribed PDP typeand APN and further providing a PDP address; mapping the requested APNto said GGSN; said GGSN configured to: provide a context response tosaid SGSN responsive to said mapped context request; and said SGSN beingfurther configured to: communicate the context response to said UE. 28.The apparatus of claim 27 wherein said GGSN is further configured toprovide a tunnel endpoint identifier (TEIP), a PDP type, a quality ofservice (QoS) and a charging ID to said SGSN as part of said contextresponse to said UE.
 29. The communication apparatus of claim 28 whereinsaid SGSN includes means for inserting a GGSN address of said GGSN andthe requested APN address as part of the PDP context, responsive to thecontext response to the UE from said GGSN.